This fails with product types because they are not in a stable order. There is already handling for order insensitive equality in

@norrietaylor since you implemented this originally, thoughts on how to resolve this? Why is ListSemanticEquals separate from Equal? Can we sort the product lines as returned from the api or is the order significant elsewhere?

Does using their plancheck interface take semantic equality into account (IIUC it should since it's just asserting there's an empty plan)

				ImportPlanChecks: resource.ImportPlanChecks{
					PreApply: []plancheck.PlanCheck{
						plancheck.ExpectEmptyPlan(),
					},
				},

Why is ListSemanticEquals separate from Equal?

That's what the Terraform framework wants. Semantically equal values will be substituted by the prior value during plan/apply and so won't trigger errors due to inconsistent state.

Can we sort the product lines as returned from the api or is the order significant elsewhere?

We can, but we're then adding a bunch of code to workaround a test framework limitation which isn't ideal. I'd be surprised if we can't implement adequate validation via ImportPlanChecks

Thanks @tobio. Do I understand correctly that just checking that there is an empty plan is the sufficient check? I've pushed a214fe4 with that change

Sorry for the late reply, yep an empty plan should be the equivalent of what ImportStateVerify accomplishes.